-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
stty: Changing shell command to add recognizing a TTY for stty tests #9336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
GNU testsuite comparison: |
|
@sylvestre The "GNU testsuite comparison" is showing now that the STTY tests are not being skipped and are running! From what I can gather about the other two tests, it appears to be just flaky tests unrelated to this change. Would you be open to taking this approach to change these five tests from "Skipped" to failed? I have other PR's open that address the failures themselves, should have these tests passing in the CI soon! |
|
Added additional comments describing the change and re-based. I'm expecting it to still fail the GNU test check since it is not able to recognize a test that moved from skipped to fail. |
|
GNU testsuite comparison: |
|
Darn compared to the other runs for some reason this time it only recognized the pty for one out of the five tests. Still some work to go |
|
Changing it to this new format appears to consistently run the STTY tests |
CodSpeed Performance ReportMerging #9336 will not alter performanceComparing Summary
Footnotes
|
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
1 similar comment
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
Two of the stty tests are now passing in the main branch! |
of course, failed is better than skipped! |
|
GNU testsuite comparison: |
|
Right now the bad-speed test is timing out making which adds too much time to the test. Once all of the stty fixes are merged this will change to seconds and should be good to merge. |
|
GNU testsuite comparison: |
|
The other change to track the skipped to failing is working now! |
Been looking into examples of how other repositories using Github actions are able to test things that require the tests recognizing that a TTY session exists. This example comes from: https://github.com/gfx/example-github-actions-with-tty and is used in a bunch of other open source projects such as: https://cocalc.com/github/Ardupilot/ardupilot/blob/master/.github/workflows/test_environment.yml
The integration test suite ran and showed that now the tests are running for stty! The tests are not passing because there is still some things to fix in STTY itself and those are being worked on in other PR's